chore: release main - #492

✨ Stainless prepared a new release

This pull request is managed by Stainless's GitHub App.

The semver version number is based on included commit messages. Alternatively, you can manually set the version number in the title of this pull request.

For a better experience, it is recommended to use either rebase-merge or squash-merge when merging this pull request.

🔗 Stainless website
📚 Read the docs
🙋 Reach out for help or questions

Greptile Summary

This release advances both packages to 0.24.0 and adds per-step observability wrappers inside business Temporal activities.

• Selects OTel-backed wrappers for Temporal business activities while retaining ambient-span tagging for dispatched start/end activities.
• Adds backend-drift warnings and focused tracing regression tests.
• Updates package manifests, generated version metadata, statistics, and changelogs.

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Begin business span] --> B{SDK tracing dispatch activity?}
    B -- Yes --> C[Tag ambient OTel activity span]
    C --> D[Persist ambient correlation IDs]
    B -- No --> E{Inside any Temporal activity?}
    E -- Yes --> F[Open per-step OTel wrapper]
    E -- No --> G[Open backend selected by mode]
    F --> H[Register wrapper handle]
    G --> H
    H --> I[End business span locally]
    I --> J[Pop and close wrapper handle]

### Issue 1
src/agentex/lib/core/tracing/trace.py:200-208
**Untracked tracing follow-up TODO**

This TODO leaves the retry roll-up and multi-replica validation work under a generic `obs-followup` label without the required ticket number or Linear link, making the deferred work difficult to locate and track.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "chore: release main" | Re-trigger Greptile}

Context used:

• Rule used - Include ticket numbers in TODO comments to make cl... (source)

Learned From
scaleapi/scaleapi#126926

• Rule used - Create Linear tasks for TODO comments in code and ... (source)

Learned From
scaleapi/scaleapi#127117